Method And System For A Temporary Secure Connection Between A Vehicle Device And An Authorized Network

ABSTRACT

A system ( 100 ) and method ( 250 ) for a temporary secure connection between a vehicle device ( 135 ) for a vehicle ( 1000 ) and wireless authorized network ( 60 ) is disclosed herein. The system ( 100 ) comprises a vehicle ( 1000 ) comprising a vehicle device ( 135 ) and a known service provider comprising a physical location ( 58 ), a server ( 56 ) and a wireless authorized network ( 60 ). The vehicle device ( 135 ) is configured to initiate an authorized transaction ( 65 ), authorized by an assigning authority ( 1105 ), for a service ( 66 ) over the wireless authorized network ( 60 ) with the known service provider ( 55 ).

CROSS REFERENCES TO RELATED APPLICATIONS

The present application is claim priority to U.S. Provisional Patent Application No. 63/405,471, filed on Sep. 11, 2022, and the Present application is also a continuation-in-part application of U.S. patent application Ser. No. 17/838,015, filed on Jun. 10, 2021, which claims priority to U.S. Provisional Patent Application No. 63/210,033, filed on Jun. 13, 2021 and now expired, and which is a continuation-in-part application of U.S. patent application Ser. No. 17/531,285, filed on Nov. 19, 2021, which claims priority to U.S. Provisional Patent Application No. 63/116,897, filed on Nov. 22, 2020 and now expired, and U.S. patent application Ser. No. 17/531,285 is also a continuation-in-part application of U.S. patent application Ser. No. 16/927,231, filed on Jul. 13, 2020, now U.S. patent Ser. No. 11/197,330, issued on Dec. 7, 2021, which claims priority to U.S. Provisional Patent Application No. 62/873,922, filed on Jul. 14, 2019, now expired, and U.S. patent application Ser. No. 16/927,231 is a continuation-in-part application of U.S. patent application Ser. No. 16/870,955, filed on May 9, 2020, now U.S. patent Ser. No. 11/330,644, issued on May 10, 2022, which is a continuation-in-part application of U.S. patent application Ser. No. 16/416,396, filed on May 20, 2019, now U.S. patent Ser. No. 10/652,935, issued on May 12, 2020, which is a continuation-in-part application of U.S. patent application Ser. No. 16/118,436, filed on Aug. 31, 2018, now U.S. patent Ser. No. 10/334,638, issued on Jun. 25, 2019, which is a continuation application of U.S. patent application Ser. No. 15/917,633, filed on Mar. 11, 2018, now U.S. patent Ser. No. 10/070,471, issued on Sep. 4, 2018, which is a continuation application of U.S. patent application Ser. No. 15/624,814, filed on Jun. 16, 2017, now U.S. Pat. No. 9,961,710, issued on May 1, 2018, which claims priority to U.S. Provisional Patent Application No. 62/352,014, filed on Jun. 19, 2016, now expired, and U.S. patent application Ser. No. 16/927,231 is a continuation-in-part application of U.S. patent application Ser. No. 16/664,906, filed on Oct. 27, 2019, now U.S. patent Ser. No. 10/803,682, issued on Oct. 13, 2020, which is a continuation application of U.S. patent application Ser. No. 15/859,380, filed on Dec. 30, 2017, now U.S. patent Ser. No. 10/475,258, issued on Nov. 12, 2019, which is a continuation-in-part application of U.S. patent application Ser. No. 15/624,814, filed Jun. 16, 2017, now U.S. Pat. No. 9,961,710, issued on May 1, 2018, which claims priority to U.S. Provisional Patent Application No. 62/352,014, filed on Jun. 19, 2016, now expired, and U.S. patent application Ser. No. 15/859,380 claims priority to U.S. Provisional Patent Application No. 62/441,290, filed on Dec. 31, 2016, now expired, U.S. Provisional Patent Application No. 62/441,298, filed on Dec. 31, 2016, now expired, and U.S. Provisional Patent Application No. 62/441,315, filed on Dec. 31, 2016, now expired, each of which is hereby incorporated by reference in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

BACKGROUND OF THE INVENTION Field of the Invention

The present invention generally relates to secure connections for vehicles.

Description of the Related Art

U.S. Pat. No. 9,215,590 for Authentication Using Vehicle Data Pairing discloses the wireless pairing of a portable device with an on-board computer of a vehicle for authenticating a transaction with a third party.

General definitions for terms utilized in the pertinent art are set forth below.

Assigning authority engine is a computer device running a software program that determines the parameters of an electric vehicle charging session based on input received over a network from the connected vehicle devices, passive devices, other devices, and/or other settings. The assigning authority engine is optionally stored in the cloud or on premise.

Beacon is a management frame that contains all of the information about a network. As specified in IEEE 802.11 for Wireless Local Area Network (WLAN), Beacon frames are periodically transmitted to announce the presence of the network. Beacon frames typically include the WLAN's service set identifier (SSID). BLUETOOTH technology is a standard short range radio link that operates in the unlicensed 2.4 gigaHertz band, defined in IEEE 802.15.1 originally an now by the Bluetooth Special Interest Group (SIG).

File Transfer Protocol (FTP) is a protocol for moving files over a network from one computer to another.

Hypertext Transfer Protocol (“HTTP”) is a set of conventions for controlling the transfer of information via the Internet from a web server computer to a client computer, and also from a client computer to a web server, and Hypertext Transfer Protocol Secure (“HTTPS”) is a communications protocol for secure communication via a network from a web server computer to a client computer, and also from a client computer to a web server by at a minimum verifying the authenticity of a web site.

Internet is the worldwide, decentralized totality of networked computers and data-transmission paths which can supply information to a connected and browser-equipped client computer, and can receive and forward information entered from the client computer.

Media Access Control (MAC) Address is a unique identifier assigned to the network interface by the manufacturer.

Memory generally includes any type of integrated circuit or storage device configured for storing digital data including without limitation ROM, PROM, EEPROM, DRAM, SDRAM, SRAM, flash memory, and the like.

Organizationally Unique Identifier (OUI) is a 24-bit number that uniquely identifies a vendor, manufacturer, or organization on a worldwide basis. The OUI is used to help distinguish both physical devices and software, such as a network protocol, that belong to one entity from those that belong to another.

Processor generally includes all types of processors including without limitation microprocessors, general purpose processors, gate arrays, array processors, application specific integrated circuits (ASICs) and digital signal processors.

Secure Connection Packet (SCP) is used to provide authentication between multiple devices or a local party and remote host to allow for secure communication or the transfer of computer files.

Service Set Identifier (SSID) is a 1 to 32 byte string that uniquely names a wireless local area network.

Transfer Control Protocol/Internet Protocol (TCP/IP) is a protocol for moving files over the Internet.

Uniform Resource Locator (URL) is an address on the World Wide Web.

User Interface (UI) is the junction between a user and a computer program. An interface is a set of commands or menus through which a user communicates with a program. A command driven interface is one in which the user enter commands. A menu-driven interface is one in which the user selects command choices from various menus displayed on the screen.

Web-Server is a computer able to simultaneously manage many Internet information-exchange processes at the same time. Normally, server computers are more powerful than client computers, and are administratively and/or geographically centralized. An interactive-form information-collection process generally is controlled from a server computer, to which the sponsor of the process has access.

There is a need for a method to create a temporary secure connection with the network to initiate an authorized transaction.

BRIEF SUMMARY OF THE INVENTION

The present invention provides a system and method for a known vehicle, with a mobile device associated with the vehicle (CVD, mobile device, or other smart/computational device), to identify (through leverage GPS and proximity sensor technology) a known network (at a defined time period) and create a temporary secure connection with the network to initiate an authorized transaction.

One aspect of the present invention is a method for a temporary secure connection between a vehicle device for a vehicle and wireless authorized network. The method includes identifying, at a vehicle device, a wireless authorized network for a known service provider. The method also includes creating a secure connection over the wireless authorized network between the vehicle device and the known service provider. The method also includes initiating an authorized transaction for a service over the wireless authorized network with the known service provider, wherein the authorized transaction is authorized by an assigning authority associated with the vehicle. The secure connection is preferably severed once the authorized transaction is validated.

Yet another aspect of the present invention is a system for a temporary secure connection between a device for a vehicle and a wireless authorized network. The system comprises a vehicle comprising a vehicle device and a known service provider comprising a physical location, a server and a wireless authorized network. The vehicle device is configured to identify a wireless authorized network for a known service provider. The vehicle device is configured to create a secure connection over the wireless authorized network between the vehicle device and the known service provider. The vehicle device is configured to initiate an authorized transaction for a service over the wireless authorized network with the known service provider, wherein the authorized transaction is authorized by an assigning authority associated with the vehicle. The secure connection is preferably severed once the authorized transaction is validated.

Having briefly described the present invention, the above and further objects, features and advantages thereof will be recognized by those skilled in the pertinent art from the following detailed description of the invention when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram of a system for a temporary secure connection between a device for a vehicle and a wireless authorized network.

FIG. 2 is a process flow diagram of a system for a temporary secure connection between a device for a vehicle and a wireless authorized network.

FIG. 3 is a flow chart for a method for a temporary secure connection between a device for a vehicle and a wireless authorized network.

FIG. 4A is an illustration of multiple sensors on a truck.

FIG. 4B is an illustration of multiple sensors on a truck connected to a BUS for the truck.

FIG. 5 is a flow chart for a method for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources.

FIG. 6A is a block diagram of a system for a secure communication protocol for connecting a wireless device to a single access point in a vehicle.

FIG. 6B is a continuation of the block diagram of FIG. 6A.

FIG. 7 is a flow chart of a method for a secure connection to a wireless network of a vehicle.

FIG. 8 is an illustration of a driver identifying a vehicle through connection of a tablet computer to an unpublished network.

FIG. 9 is an isolated view of general electrical components of a mobile communication device.

FIG. 10 is an isolated view of general electrical components of a server.

FIG. 11 is a flow chart of a method for securely connecting a wireless device to a single access point in a vehicle.

DETAILED DESCRIPTION OF THE INVENTION

One embodiment is a method for a temporary secure connection between a vehicle device for a vehicle and a wireless authorized network. The method 250, in FIG. 3 , includes identifying, at a vehicle device, a wireless authorized network for a known service provider in step 251. The method also includes step 252, creating a secure connection over the wireless authorized network between the vehicle device and the known service provider. The method also includes initiating an authorized transaction for a service over the wireless authorized network with the known service provider, in step 253. The authorized transaction is authorized by an assigning authority associated with the vehicle.

In reference to FIG. 2 , the method also includes transmitting 67 sale and purchase information for the authorized transaction 65. The method also includes validating 68 the wireless authorized network based 60 on proximity 69 to the known service provider 55 and the initiation 70 of the service 66. The method also includes confirming 71 the end of the service. The method also includes validating 72 the end of the authorized transaction based on the end of the service 73 and proximity to the known service provider 74.

The method also includes guiding the vehicle to the known service provider utilizing macro-navigation to travel from an origination site to a macro/micro route interface. The method also includes initiating a micro-navigation guidance protocol upon approach to the macro/micro route interface and guiding the vehicle using the micro-navigation guidance protocol from the macro/micro route interface to a terminal location within a destination site.

Validating 72 the end of the authorized transaction further comprises verifying 75 an hours of service for the known service provider and confirming 76 that the authorized transaction occurs within a time period of the hours of service. Proximity to the known service provider is preferably validated utilizing a GPS component of the vehicle. Proximity to the known service provider is alternatively validated utilizing miles traveled by the vehicle from a previous known location. The secure connection is preferably severed once the authorized transaction is validated.

Another embodiment is a system for a temporary secure connection between a device for a vehicle and a wireless authorized network, as shown in FIG. 1 . The system 100 comprises a vehicle 1000 comprising a vehicle device 135 and a known service provider 55 comprising a physical location 58, a server 56 and a wireless authorized network 60. The vehicle device 135 is configured to identify a wireless authorized network 60 for a known service provider 55. The vehicle device 135 is configured to create a secure connection over the wireless authorized network 60 between the vehicle device 135 and the known service provider 55. The vehicle device 135 is configured to initiate an authorized transaction 65 for a service 66 over the wireless authorized network 60 with the known service provider 55, wherein the authorized transaction 65 is authorized by an assigning authority 1105 associated with the vehicle 1000.

In reference to FIG. 2 , the vehicle device 135 is configured to transmit 67 sale and purchase information for the authorized transaction 65. The vehicle device 135 is preferably configured to validate 68 the wireless authorized network 60 based on proximity 70 to the known service provider 55 and the initiation 69 of the service 66. The vehicle device 135 is preferably configured to confirm 71 the end of the service. The vehicle device 135 is alternatively configured to validate 72 the end of the authorized transaction based on the end of the service 73 and the proximity to the known service provider 74. The vehicle device 135 is preferably configured to verify 75 an hours of service for the known service provider 55 and to confirm 76 that the authorized transaction 65 occurs within a time period of the hours of service. The vehicle device is preferably configured to guide the vehicle to the known service provider utilizing macro-navigation to travel from an origination site to a macro/micro route interface. The vehicle device is preferably configured to initiate a micro-navigation guidance protocol upon approach to the macro/micro route interface and guiding the vehicle using the micro-navigation guidance protocol from the macro/micro route interface to a terminal location within a destination site.

The vehicle device is preferably a connected vehicle device (CVD) 135 or a mobile device 110, as shown in FIG. 1 .

The secure connection is preferably made to a server 56 for the known service provider 55.

The service 66 is preferably for fuel for the vehicle 1000 and the confirmation of the end of the service is the confirmation that the fuel was dispensed into a tank of the vehicle. The service is alternatively for repair of the vehicle and the confirmation of the end of the service is the confirmation that the vehicle is operating properly.

The initiation of service and proximity to provider are validators for the start of the transaction, while the end of service and proximity to provider are validators for the end of the transaction. The provider and device owner then pass sale and purchase information for the transaction being provided to the vehicle or driver. (This would require no localized physical transaction from the driver of the vehicle.) This transaction confirms that fuel was dispensed into the known vehicle using data from the vehicle (CAN BUS) for validation.

A driver drives to a fuel pump or other service provider, receives service and (hives away. This interaction minimizes the physical interaction needed for the transaction and validate that the transaction is occurring as expected using data validation, providing convenience for the driver and fraud oversight for the transaction.

For a tether connection, the approval of the connection (certification) can be limited to time period, HOS; recognize that it is approved retailer/partner; or proximity paradigm-proximity connection.

Examples of vehicle to authorized connections (retailers): Access—Provide temporary connection for physical access and/or data at an infrastructure point (e.g., gate); Diagnostic and maintenance—Information from (ND could be downloaded to authorized repair shop and decide/identify repair/maintenance requirements; Mechanical/physical—Use for weigh ins; Transactional—Providing transactional data, such as payment information (fuel, services (washing) other); Technical—App or firmware update for updating process (log in requirement, EV).

Other uses include: Tracking; Location assist—precision; Fraud aversion, asset tracking; Health information; Authorized expenses; Video transfer; and/or CVD tethering to partners for transferring apps.

In another embodiment, the system includes a vehicle 1000, an assigning authority engine 1105, a remote profile manager (RPM) toolset 1130 with an RPM sync program 1135, and a plurality of databases, both accessible through the cloud. The vehicle 1000 preferably includes a connected vehicle device (CVD) 135. The remote profile manager toolset 1130 preferably includes a server. The plurality of databases is preferably composed of multiple databases.

The authorized transaction is authorized by assigning authority engine 1105 for a specific vehicle 1000. In a preferred embodiment, the assigning authority engine 1105 resides at a server for the system, and the RPM toolset 1130 resides at a separate server. Alternatively, the assigning authority engine 1105 and the RPM toolset 1130 reside at the same server. The assigning authority engine 1105 is preferably configured to access and combine off-vehicle content and on-vehicle data, along with the work assignment, to produce dynamic, temporal combinations of data elements and instructions for the vehicle 1000. Additionally, the assigning authority engine 1105 provides permission to various applications to share data for app-to-app integration. In one example, the assigning authority engine 1105 grants permission to a workflow application running on a mobile communication device for the vehicle 1000 to obtain data from a navigation application running on the mobile communication device. The assigning authority engine 1105 instructs the navigation application to share the data with the workflow application. In one specific example, the shared data is GPS coordinates for the vehicle.

A set of sources of data for remote profile management for a vehicle can include vehicles, devices, operations, assignments, third parties, software apps, miscellaneous and other.

Cloud sources include a main protected server/cloud, an original equipment manufacturer server/cloud, a customer server/cloud and a public server/cloud. Multiple other servers/clouds and/or databases can be utilized with the present invention without departing from the scope and spirit of the claims. The cloud sources, databases, RPM and assigning authority engine communicate with the CVD utilizing various wireless communication protocols including WiFi, cellular networks, BLUETOOTH, GPS, and the like. The contents of each of the databases and cloud sources are accessible and combinable by the assigning authority engine 1105 to produce dynamic, temporal combinations of data elements and instructions for the vehicle 1000. The assigning authority engine 1105 is configured to use the remote profile manager toolset 1130 to execute the dynamic, temporal combinations. The dynamic, temporal combinations access data from the cloud sources comprising third party data and vehicle, timing, event, and/or positioning (“VTEP”) data to inform instruction sets delivered by the assigning authority engine. The instruction sets are preferably temporal permission for the on-vehicle sources and off-vehicle sources (e.g., applications) to connect and share data with each other. One or more elements of the VTEP data is used as the basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. A single coherent information picture is formed from fusing data and computational information from the on-vehicle and the off-vehicle sources. The new information data set combination (single coherent information picture) is a display of information generated from the combination of data from the on-vehicle sources and the off-vehicle sources from known service providers. The data set can include dynamic route information (road condition changes due to weather, construction and the like), an updated driver's profile, vehicle engine date, cargo data, dynamic compliance rules, micro-navigation data, fuel stop data, inspection stations on the route, wireless communications connectivity status, time to destination, and the like. An example of a new information data set combination is imparting GPS location data from a truck/CVD onto cargo (the potato chips example). The new information data set combination is preferably any new combination of the connected data sources data for the specific vehicle of interest.

The vehicle 1000 has multiple endpoints with direct connectivity to the CVD 135, and requires no routing through a cloud service. The endpoints are user interfaces or built-in displays, devices connected through fixed or wireless connection to the vehicle's CVD 135, sensors connected through a vehicle bus 105 (see FIG. 4B) to the CVD 135, or directly to the CVD 135 via wired or wireless connection, like devices. The vehicle 1000 is preferably a primary generator and source of VTEP data.

The RPM 1130 preferably comprises an RPM sync 1135 for syncing with other devices, servers, the Cloud, the CVD and the like.

The real-time data for the vehicle 1000 preferably comprises a real-time speed of the vehicle, tire pressure values from a plurality of tire sensors, refrigeration/HVAC unit values, a plurality of fluid levels, a plurality of power unit values, a real-time fuel tank capacity, and a fuel type.

The plurality of configurable real-time vehicle data trigger events comprises a value outside of a predetermined range for the real-time data of the vehicle.

The real-time driver/operator profile comprises amount of time driving during a pre-determined time period, number of rest breaks during the pre-determined time period, license compliance data, physical disabilities and driving violations.

One example of a known service provider 55 is a fuel stop. A profile of a fuel stop preferably comprises real-time types of fuels available, set billing instructions, physical dimensions of a plurality of fuel pumps, GPS coordinates, hours of operation, food service availability, and resting area availability. The predetermined fueling time period is a time range to fuel the vehicle based on the real-time GPS location of the vehicle, the real-time speed of the vehicle, the distance to the selected fuel stop from the real-time GPS location of the vehicle, and the hours of operation of the fuel stop.

A configuration of the vehicle 1000 is preferably selected from one of a single trailer, a dual trailer, a triple trailer, and a refrigeration trailer.

Another example of an off-vehicle source is a database (Federal, State local) with dynamic compliance rules. The dynamic compliance rules comprise speed limits, transport of toxic waste, the transport of refrigerated cargo, the rest durations for drivers/operators, the necessary insurance coverage, and the type of taxes and fees to be paid.

The workflow utilized by the assigning authority engine 1105 preferably comprises an origination location of the vehicle, a destination of the vehicle, a route to the destination, a cargo, a time of departure and a time of arrival.

In one non-limiting example, the assigning authority engine 1105 receives data over the cloud from a customer server that a shipment of bags of potato chips were damaged in transit. The assigning authority engine 1105 accesses a CVD 135 or mobile device for the vehicle that delivered the bags of potato chips to determine the origination location, the destination location and the route. The assigning authority engine 1105 uses a navigation app on the mobile device (tablet computer) to determine the route, and an elevation of the route. The assigning authority engine 1105 determines that the vehicle traveled over a high elevation mountain range that probably resulted in the damage to the bags of potato chips due to a pressure differential. The assigning authority engine 1105 uses this information to reroute a subsequent shipment of bags of potato chips to avoid the high elevation mountain range.

FIG. 4A is an illustration of multiple sensors on a truck 1000. The vehicle/truck 1000 preferably comprises an oil level sensor 1005, an engine sensor 1010, a power sensor 1015, a refrigeration/HVAC sensor 1020, a temperature sensor 1025, a tire pressure sensor 1030, and a fuel sensor 1035. Those skilled in the pertinent art will recognize that multiple other sensors may be utilized without departing from the scope and spirit of the present invention. FIG. 4B is an illustration of multiple sensors on a truck connected to a data bus 105 for the truck. Each of the sensors (oil level sensor 1005, engine sensor 1010, a power sensor 1015, a refrigeration/HVAC sensor 1020, a temperature sensor 1025, tire pressure sensors 1030 a-d, and fuel sensor 1035) is preferably connected to the data bus 105 for transferring data to an on-board computer of the vehicle 1000, or directly to the CVD 135. Alternatively, some or all of the sensors use wireless communications to communication with the CVD 135.

FIG. 5 is a flow chart for a method 500 for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources for validating transactions. At block 501, the contents of each of a plurality of databases are accessed by an assigning authority engine. At block 502, the contents are combined to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instruction sets for a vehicle. At block 503, the plurality of dynamic, temporal combinations is executed. At block 504, data from a plurality of cloud sources comprising third party data and vehicle, timing, event, and/or positioning (“VTEP”) data is accessed to inform the plurality of instruction sets delivered by the assigning authority engine to the RPM. At block 505, one or more elements of the VTEP data is used as a basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. At block 506, a single coherent information picture is formed from fusing data and computational information from the on-vehicle and the off-vehicle sources.

FIG. 6A and FIG. 6B show a system 10 for securely connecting a wireless device to a single access point in a vehicle for a predetermined work assignment and for a temporary secure connection between a vehicle device for a vehicle and wireless authorized network. The system 10 preferably comprises a remote server (cloud) 11, a vehicle gateway device 130, a smart device 110, and a passive device 61. The vehicle gateway device 130 is preferably a connected vehicle device (“CVD”) 135.

The server/cloud 11 accesses dataset 12 and obtains driver information. Vehicle information, mobile device information (MAC address), passive device information (beacon ID), and other information to compile a SCP packet 14. At block 15, the server 11 provides SCP definitions to the vehicle gateway device 130 and the mobile device 110. At block 16 the server/cloud 11 authorizes the SCP. At block 17, the server/cloud 11 communicates with the vehicle gateway device 130.

The vehicle gateway device 130 compiles a CVD compiled SCP packet 25 using datasets 22, the beacon ID 23, a scan of wireless devices 24, and the SCP definitions 26 received from the server/cloud 11. The CVD compiled SCP packet is sent to the cloud/server 11 at block 16 and authorization/validation of the CVD compiled SCP packet is received at block 27. At block 28 the SCP is authorized for broadcasting at the vehicle gateway device 130 a wireless network with a hidden and hashed SSID unique to the vehicle, the hidden and hashed SSID generated from the validated SCP packet. At block 29, the vehicle gateway device 130 communicates the broadcast with the server/cloud 11. At block 31, the vehicle gateway device 130 communicates with other devices, namely the smart device 110 over preferably a WiFi hotspot 32 and the passive device 61 by pairing using a BLUETOOTH communication protocol at block 33.

At block 49, the smart device (mobile device) 110 compiles a complied mobile device SCP packet from the SCP definitions 42, the data sets 48, the beacon ID 43, the Tablet ID 45, a driver ID 46, a vehicle ID 47 and scan of wireless devices 44. The mobile device 110 generates the hashed SSID and a passphrase from the complied mobile device SCP packet. At block 51, the mobile device 110 connects to the WiFi hotspot 32 of the vehicle gateway 130.

The passive device 61 broadcast a unique ID at block 62 which is received by the mobile device 110 and the vehicle gateway device 130. At block 63, if a BLUETOOTH device, it broadcasts a BLUETOOTH advertisement at block 64.

The SCP is defined by an assigning authority in the server/cloud 11. The server/cloud 11 sends the SCP definition and any other required data in datasets to the CVD 135 and the mobile device 110. The CVD 135 adds the contextual data from local datasets to the sever-sent data to compile its SCP based definition. The local datasets include data wirelessly scanned from passive devices, preferably transmitting a BLUETOOTH beacon. Other local datasets include information from the vehicle. The CVD 135 sends its compiled SCP packet to the server 11 for authorization. The server 11 verifies the CVD compiled SCP packet, and if valid, the server 11 transmits a validation/approval signal to the CVD 135. The CVD then generates an access point SSID/passphrase with SCP. Likewise, the mobile device 110 utilizes contextual data from local datasets to compile its SCP based on the definitions. The mobile device 110 connects to the access point of the CVD 135 using the SCP. The CVD 135 and the mobile device 110 also connect to the passive device 61 since it is part of the SCP definition.

As used by the assigning authority engine 1105, a predetermined work assignment is a temporal event with a fixed start and completion based on assignable boundary conditions. The assignable boundary condition is at least one of a predetermined time period, a geographical destination, and a set route. Alternatively, the assignable boundary condition is any feature with a beginning and a termination. The assigning authority is performed by a person or persons, who have the appropriate authority and mechanisms to assign specific tasks and assets to a specific vehicle: and vehicle operator or custodian, and to assign workflow assignments to same. The predetermined work assignment is assigned to a known person or entity that has its own primary networked device accessible through a password protected user interface, a specific name and password that auto-populates or otherwise automatically satisfies a plurality of credentials requirements, wherein the plurality of credential requirements are automatically available or revoked based on the assignable boundary condition identified in a pairing event.

The CVD 135 preferably broadcasts a WiFi wireless network with a hidden and hashed SSID unique to the host vehicle and protected by a unique, dynamically generated and hashed passphrase. The vehicle ID is entered into an application on the tablet that is then converted to the same hashed SSID and passphrase, which allows the tablet to attempt to connect to the corresponding CVD's WIFI network and begin communication.

A method 900 for a secure connection to a wireless network of a vehicle is shown in FIG. 7 . In preferred embodiment, once a secure connection is established with a wireless network of the vehicle, then a temporary secure connection between a vehicle device and wireless authorized network can be established. At block 901, a server generates definitions for a SCP packet for assigning authority for a vehicle. At block 902 the server transmits the definitions for the SCP packet to a CVD and a mobile device. At block 903, the CVD compiles the SCP packet to generate a CVD compiled SCP. At block 904, the CVD transmits the CVD compiled SCP to the server for authorization. At block 905, the server transmits authorization for the CVD compiled SCP from to the CVD for creation of a validated SCP. At block 906, the mobile device generates a dataset to compile a mobile device compiled SCP. At block 907, the CVD broadcasts at a wireless network with a hidden and hashed SSID unique to the vehicle. The hidden and hashed SSID is generated from the validated SCP packet. At block 908, the mobile device generates the hashed SSID and a passphrase from the dataset, which allows the mobile device connect to the wireless network. At block 909, the mobile device searches for a vehicle having the CVD broadcasting the wireless network in a hidden mode. At block 910, the mobile device securely connects with the CVD.

One embodiment utilizes a system for vehicle to mobile device secure wireless communications. The system comprises a vehicle 1000, a CVD 135, a mobile device 110 and a passive communication device 61. The vehicle 1000 comprises an on-board computer with a memory having a vehicle identification number (VIN), a connector plug, and a motorized engine. The CVD 135 comprises a processor, a WiFi radio, a BLUETOOTH radio, a memory, and a connector for mating with the connector plug of the vehicle. The mobile device 110 comprises a graphical user interface, a mobile application, a processor, a WiFi radio, and a cellular network interface. The passive communication device 61 operates on a BLUETOOTH communication protocol. The server 11 is configured to generate a plurality of definitions for a SCP packet for assigning authority for the vehicle. The server 11 is configured to transmit the plurality of definitions for the SCP packet from the server to the CVD 135 and the mobile device 110. The CVD 135 is configured to compile the SCP packet to generate a CVD compiled SCP. The CVD 135 is configured to transmit the CVD compiled SCP to the server 11 for authorization. The server 11 is configured to transmit authorization for the CVD compiled SCP to the CVD 135 for creation of a validated SCP. The mobile device 110 is configured to generating a dataset to compile a mobile device compiled SCP. The CVD 135 is configured to broadcast a wireless network with a hidden and hashed SSID unique to the vehicle, the hidden and hashed SSID generated from the validated SCP packet. The mobile device 110 is configured to generate the hashed SSID and a passphrase from the dataset, which allows the mobile device connect to the wireless network. The mobile device 110 is configured to search for a vehicle having the CVD broadcasting the wireless network in a hidden mode. The mobile device 110 is configured to connect to the CVD 135 over the wireless network.

The dataset preferably comprises at least one of a plurality of definitions for the SCP packet, a tablet ID, a driver ID, a vehicle ID, a beacon ID, identified or defined entity/participant to the transaction, descriptions, actions, or states of thing, characteristics of identifiable devices, when present in a certain proximity and/or context.

Optionally, the mobile device 110 connects to a passive device, the passive device operating on a BLUETOOTH communication protocol. The passive device 61 is preferably a BLUETOOTH enabled device advertising a unique ID as a beacon or a complex system (speaker, computer, etc.) that emits BLUETOOTH enabled device advertising a unique ID as a beacon.

The mobile device 110 preferably receives input from a driver of the vehicle, and/or the server 11 contains the assigning authority that generates the SCP definitions.

The passive device 61 is preferably an internal device in the vehicle or an external device posted on a gate to a facility and generating a beacon. The beacon from the passive device is preferably a mechanism to ensure that the connection between the mobile device 110 and the CVD 135 occurs at a specific physical location dictated by the assigning authority through the server 11. Preferably, the automatic connection between the mobile device 110 and the CVD 135 occurs because the assigning authority, through the server, has dictated that it occur.

FIG. 8 illustrates a staging yard for trucks 210 a-201 d that will generate a temporary secure connection between a vehicle device for a vehicle and wireless authorized network for an authorized transaction. Each of a multitude of trucks 210 a-210 d broadcast a wireless signal for a truck specific network, with one truck 210 c broadcasting a wireless signal 225. However, the SSID is not published so unless a driver is already in possession of the SSID, the driver 205 will not be able to pair the tablet computer 110 with the CVD 135 of the truck 210 to which the driver 205 is assigned. So even though the wireless signals are being “broadcast”, they will not appear on a driver's tablet computer 110 (or other mobile device) unless the tablet computer 110 has already been paired with the CVD 135 of the vehicle 210. A driver 205 in possession of a tablet computer 110 pairs, using a signal 230, the tablet computer 110 with the wireless network 225 of the CVD of the truck 210 c, and thus the driver locates the specific truck 210 c he is assigned to in a parking lot full of identical looking trucks 210 a-d.

For example, on an IPHONE® device from Apple, Inc., the “UDID,” or Unique Device Identifier is a combination of forty numbers and letters, and is set by Apple and stays with the device forever.

For example, on an ANDROID based system, one that uses Google Inc.'s ANDROID operating system, the ID is set by Google and created when an end-user first boots up the device. The ID remains the same unless the user does a “factory reset” of the phone, which deletes the phone's data and settings.

The mobile communication device 110, or mobile device, is preferably selected from mobile phones, smartphones, tablet computers, PDAs and the like. Examples of smartphones and the device vendors include the IPHONE® smartphone from Apple, Inc., the DROID® smartphone from Motorola Mobility Inc., GALAXY S® smartphones from Samsung Electronics Co., Ltd., and many more. Examples of tablet computing devices include the IPAD® tablet computer from Apple Inc., and the XOOM™ tablet computer from Motorola Mobility Inc.

The mobile communication device 110 then a communication network utilized preferably originates from a mobile communication service provider (aka phone carrier) of the customer such as VERIZON, AT&T, SPRINT, T-MOBILE, and the like mobile communication service providers, provide the communication network for communication to the mobile communication device of the end user.

Wireless standards utilized include 802.11a, 802.11b, 802.11g, AX.25, 3G, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, 802.15, 802.16, and IrDA.

BLUETOOTH™ technology operates in the unlicensed 2.4 GHz band of the radio-frequency spectrum, and in a preferred embodiment the secondary device 30 and/or primary device 25 is capable of receiving and transmitting signals using BLUETOOTH™ technology. LTE Frequency Bands include 698-798 MHz (Band 12, 13, 14, 17); 791-960 MHz (Band 5, 6, 8, 18, 19, 20); 1710-2170 MHz (Band 1, 2, 3, 4, 9, 10, 23, 25, 33, 34, 35, 36, 37, 39); 1427-1660.5 MH (Band 11, 21, 24); 2300-2700 MHz (Band 7, 38, 40, 41); 3400-3800 MHz (Band 22, 42, 43), and in a preferred embodiment the secondary device 30 and/or the primary device 25 is capable of receiving and transmitting signals using one or more of the LTE frequency bands. WiFi preferably operates using 802.11a, 802.11b, 802.11g, 802.11n communication formats as set for the by the IEEE, and in in a preferred embodiment the secondary device 30 and/or the primary device is capable of receiving and transmitting signals using one or more of the 802.11 communication formats. Near-field communications (NFC) may also be utilized.

As shown in FIG. 9 , a typical mobile communication device 110 preferably includes an accelerometer 301, I/O (input/output) 302, a microphone 303, a speaker 304, a GPS chipset 305, a Bluetooth component 306, a Wi-Fi component 307, a 3G/4G component 308, RAM memory 309, a main processor 310, an OS (operating system) 311, applications/software 312, a Flash memory 313, SIM card 314, LCD display 315, a camera 316, a power management circuit 317, a battery 318 or power source, a magnetometer 319, and a gyroscope 320. Each of the interface descriptions preferably discloses use of at least one communication protocol to establish handshaking or bi-directional communications. These protocols preferably include but are not limited to XML, HTTP, TCP/IP, Serial, UDP, FTP, SFTP, SCP, RSync, Web Services, WAP, SMTP, SMPP, DTS, Stored Procedures, Import/Export, Global Positioning Triangulation, IM, SMS, MMS, GPRS, WebDAP, and Flash. Databases that may be used with the system preferably include but are not limited to MSSQL, Access, MySQL, Progress, Oracle, DB2, Redis, MongoDB, Amazon Aurora, Amazon Redshift, Amazon RDS, Amazon DynamoDB, Apache Hadoop, Open Source DBs and others. Operating system used with the system preferably include Microsoft 2010, XP, Vista, 200o Server, 2003 Server, 2008 Server, Windows Mobile, Linux, Android, Unix, I series, AS 400 and Apple OS.

The underlying protocol at the cloud server 11, is preferably Internet Protocol Suite (Transfer Control Protocol/Internet Protocol (“TCP/IP”)), and the transmission protocol to receive a file is preferably a file transfer protocol (“FTP”), Hypertext Transfer Protocol (“HTTP”), Secure Hypertext Transfer Protocol (“HTTPS”) or other similar protocols. The transmission protocol ranges from SIP to MGCP to FTP and beyond. The protocol at the authentication server is most preferably HTTPS.

Wireless standards include 802.11a, 802.11b, 802.11g, AX.25, 3G, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, 802.15, 802.16, and IrDA.

Components of a cloud computing server 11 of the system, as shown in FIG. 10 , preferably includes a CPU component 401, a graphics component 402, PCI/PCI Express 403, memory 404, non-removable storage 407, removable storage 408, Network Interface 409, including one or more connections to a fixed network, and SQL database(s) 415 a-415 d, which includes the venue's CRM. Included in the memory 404, is an operating system 405, a SQL server 406 or other database engine, and computer programs/software 410. The server 40 also preferably includes at least one computer program configured to receive data uploads and store the data uploads in the SQL database. Alternatively, the SQL server 406 can be installed in a separate server from the server 11.

Cloud service providers optionally used in the present invention include Amazon Web Services (AWS), Google Compute Engine (GCE), Microsoft Azure, Digital Ocean, CloudFlare, Akamai, IBM Cloud, Oracle Cloud Infrastructure, and similar.

A flow chart for an alternative method 600 for a secure connection to a wireless network of a vehicle is shown in FIG. 11 . In preferred embodiment, once a secure connection is established with a wireless network of the vehicle, then a temporary secure connection between a vehicle device and wireless authorized network can be established. At block 601, the CVD broadcasts an encrypted, blind SSID based on specific vehicle data. At block 602, leveraging the known vehicle data and the encryption algorithm a mobile device searches for a vehicle having a CVD broadcasting the wireless network. At block 603, the mobile device is connected with the CVD.

In one embodiment, the off-vehicle source is a mobile application operating on a mobile device, and the data originates from the mobile application.

In another embodiment, app to app integration is utilized to generate the information data set. The app to app integration is performed at a remote server, within an app on a mobile device, on a CVD or a combination thereof.

The cloud sources preferably comprise a public cloud source, a private cloud source, a hybrid cloud source, a multi-cloud source, a service provider cloud, a telematics service provider cloud, an original equipment manufacturer cloud (truck manufacturer, Tier 1 supplier, device supplier and the like), a customer cloud (end user) and/or a public cloud.

The system also preferably includes physical infrastructures with communication devices comprising at least one of a building, a gate, an access controlled point of entry, a parking structure, a weigh station, a toll collection structure, a fueling equipment and a vehicle service equipment. In one embodiment, a passive device on a physical structure broadcasts a unique ID which is received by a mobile device and a vehicle gateway device. In one embodiment, the passive device is a BLUETOOTH that broadcasts a BLUETOOTH advertisement.

The vehicle 1000 is preferably one of a long-haul semi-truck, a bus, a sedan, a pick-up, a sports utility vehicle, a limousine, a sports car, a delivery truck, a van, or a mini-van.

In one example for a temporary secure connection between a vehicle device for a vehicle and wireless authorized network, a vehicle begins at an origination location. The vehicle will travel on a route to a destination location. Along the route are multiple fuels stops. A GPS satellite provides GPS location information to the vehicle. The vehicle is in communication with a server over a communication network. The server receives a workflow for a vehicle. The workflow comprises an origination location of the vehicle, a destination of the vehicle, a route to the destination, a cargo, a time of departure and a time of arrival. The server calculates a fuel stop for the vehicle based on an authorized fuel stop (an authorized retailer with an authorized network and an established relationship with the vehicle entity) the workflow, the real-time operator profile, the configuration of the vehicle, the real-time GPS location of the vehicle (received from the vehicle), the real-time vehicle data, a dynamic compliance rule, and the selected fuel station profile. The server transmits to the vehicle over the communication network the guidance to the selected fuel stop from the current location of the vehicle. The guidance includes micro-navigation to an exact fuel pump contained within the fuel stop location of the fuel stop for fueling during a predetermined fueling time period. A secure connection over the wireless authorized network between the vehicle device and the known service provider is created. An authorized transaction is initiated for a service over the wireless authorized network with the fuel stop, wherein the authorized transaction is authorized by an assigning authority associated with the vehicle.

An operating system controls the execution of other computer programs, running of the PSO platform, and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The operating system may be, for example Windows (available from Microsoft, Corp. of Redmond, Wash.), LINUX or other UNIX variants (available from Red Hat of Raleigh, N.C. and various other vendors), Android and variants thereof (available from Google, Inc. of Mountain View, Calif.), Apple OS X, iOs and variants thereof (available from Apple, Inc. of Cupertino, Calif), or the like.

The system and method described in connection with the embodiments disclosed herein is preferably embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module preferably resides in flash memory, ROM memory, EPROM memory, EEPROM memory, RAM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is preferably coupled to the processor, so that the processor reads information from, and writes information to, the storage medium. In the alternative, the storage medium is integral to the processor. In additional embodiments, the processor and the storage medium reside in an Application Specific Integrated Circuit (ASIC). In additional embodiments, the processor and the storage medium reside as discrete components in a computing device. In additional embodiments, the events and/or actions of a method reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer-readable medium, which are incorporated into a computer software program.

In additional embodiments, the functions described are implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions are stored or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium is any available media that is accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures, and that can be accessed by a computer. Also, any connection is termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. “Disk” and “disc”, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and BLU-RAY disc where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable medium.

A computer program code for carrying out operations of the Present Invention is preferably written in an object oriented, scripted or unscripted programming language such as C++, C #, SQL, Java, Python, Javascript, Typescript, PHP, Ruby, or the like.

Each of the interface descriptions preferably discloses use of at least one communication protocol to establish handshaking or bi-directional communications. These protocols preferably include but are not limited to XML, HTTP, TCP/IP, Serial, UDP, FTP, Web Services, WAP, SMTP, SMPP, DTS, Stored Procedures, Import/Export, Global Positioning Triangulation, IM, SMS, MMS, GPRS and Flash. The databases used with the system preferably include but are not limited to MSSQL, Access, MySQL, Oracle, DB2, Open Source DBs and others. Operating system used with the system preferably include Microsoft 2010, XP, Vista, 200o Server, 2003 Server, 2008 Server, Windows Mobile, Linux, Android, Unix, I series, AS 400 and Apple OS.

The underlying protocol at a server, is preferably Internet Protocol Suite (Transfer Control Protocol/Internet Protocol (“TCP/IP”)), and the transmission protocol to receive a file is preferably a file transfer protocol (“FTP”), Hypertext Transfer Protocol (“HTTP”), Secure Hypertext Transfer Protocol (“HTTPS”), or other similar protocols. The protocol at the server is preferably HTTPS.

Components of a server includes a CPU component, a graphics component, memory, non-removable storage, removable storage, Network Interface, including one or more connections to a fixed network, and SQL database(s). Included in the memory, is an operating system, a SQL server or other database engine, and computer programs/software.

-   Kennedy et al., U.S. patent Ser. No. 11/197,329 for a Method And     System For Generating Fueling Instructions For A Vehicle, is hereby     incorporated by reference in its entirety. -   Kennedy et al., U.S. patent Ser. No. 10/652,935 for Secure Wireless     Networks For Vehicles, is hereby incorporated by reference in its     entirety. -   Kennedy et al., U.S. patent Ser. No. 11/330,644 for Secure Wireless     Networks For Vehicle Assigning Authority, is hereby incorporated by     reference in its entirety. -   Kennedy et al., U.S. patent Ser. No. 10/917,921 for Secure Wireless     Networks For Vehicles, is hereby incorporated by reference in its     entirety. -   Son et al., U.S. patent Ser. No. 10/475,258 for a Method And System     For Utilizing Vehicle Odometer Values And Dynamic Compliance, is     hereby incorporated by reference in its entirety. -   Son et al., U.S. patent Ser. No. 10/070,471 for a Secure Wireless     Networks For Vehicles, is hereby incorporated by reference in its     entirety. -   Son et al., U.S. patent Ser. No. 10/652,935 for a Secure Wireless     Networks For Vehicles, is hereby incorporated by reference in its     entirety. -   Kennedy et al., U.S. patent Ser. No. 11/197,330 for a Remote Profile     Manager For A Vehicle, is hereby incorporated by reference in its     entirety. -   Kennedy et al., U.S. patent Ser. No. 11/438,938 for a System And     Method To Generate Position And State-Based Electronic Signaling     From A Vehicle, is hereby incorporated by reference in its entirety. -   Kennedy et al., U.S. Patent Publication Number 20200413458 (U.S.     patent application Ser. No. 17/022,027, filed on Sep. 15, 2020) for     a Micro-Navigation For A Vehicle, is hereby incorporated by     reference in its entirety. -   Kopchinsky et al., U.S. Patent Publication Number 20220046728 (U.S.     patent application Ser. No. 17/384,768, filed on Jul. 25, 2021) for     a Method And System For Dynamic Wireless Connection Management, is     hereby incorporated by reference in its entirety. -   Fields et al., U.S. Patent Publication Number 20220086924 (U.S.     patent application Ser. No. 17/486,777, filed on Sep. 27, 2021) for     Remote Mobile Device Management, is hereby incorporated by reference     in its entirety. -   Kennedy et al, U.S. Patent Publication Number 20220104288 (U.S.     patent application Ser. No. 17/498,689, filed on Oct. 11, 2021) for     a Method And System For Synchronizing Events Within A Secure     Wireless Network, is hereby incorporated by reference in its     entirety. -   Kopchinsky et al., U.S. Patent Publication Number 20220078861 (U.S.     patent application Ser. No. 17/531,285, filed on Nov. 19, 2021) for     a Method And System For Generating Standardized Format Data From     Disparate, Non-Standardized Vehicle Data, is hereby incorporated by     reference in its entirety. -   Kopchinsky et al., U.S. Patent Publication Number 20220304082 (U.S.     patent application Ser. No. 17/697,896, filed on Mar. 17, 2022), for     an Assigning Authority For Electric Vehicle Charging, is hereby     incorporated by reference in its entirety. -   Abella et al. U.S. Patent Publication Number 20220330353 (U.S.     patent application Ser. No. 17/718,215, filed on Apr. 11, 2022), for     a Method And System To Identify And Mitigate Problematic Devices,     which is hereby incorporated by reference in its entirety. -   Kopchinsky et al., U.S. Patent Publication Number 20220400523 (U.S.     patent application Ser. No. 17/838,015, filed on Jun. 10, 2022), for     Dynamic Connection Management, is hereby incorporated by reference     in its entirety. -   Fields et al., U.S. Patent Publication Number 20230254911 (U.S.     patent application Ser. No. 18/136,666, filed on Apr. 19, 2023), for     System And Method For Monitoring And Minimizing Vehicle Carbon     Emissions, is hereby incorporated by reference in its entirety.

From the foregoing it is believed that those skilled in the pertinent art will recognize the meritorious advancement of this invention and will readily understand that while the present invention has been described in association with a preferred embodiment thereof, and other embodiments illustrated in the accompanying drawings, numerous changes modification and substitutions of equivalents may be made therein without departing from the spirit and scope of this invention which is intended to be unlimited by the foregoing except as may appear in the following appended claim. Therefore, the embodiments of the invention in which an exclusive property or privilege is claimed are defined in the following appended claims. 

We claim as our invention the following:
 1. A method for a temporary secure connection between a vehicle device for a vehicle and wireless authorized network, the method comprising: identifying, at a vehicle device, a wireless authorized network for a known service provider; creating a secure connection over the wireless authorized network between the vehicle device and the known service provider; and initiating an authorized transaction for a service over the wireless authorized network with the known service provider, wherein the authorized transaction is authorized by an assigning authority associated with the vehicle.
 2. The method according to claim 1 further comprising transmitting sale and purchase information for the authorized transaction.
 3. The method according to claim 1 further comprising validating the wireless authorized network based on proximity to the known service provider and the initiation of the service.
 4. The method according to claim 3 further comprising confirming the end of the service.
 5. The method according to claim 4 further comprising validating the end of the authorized transaction based on the end of the service and proximity to the known service provider.
 6. The method according to claim 5 wherein the service is for fuel for the vehicle and the confirmation of the end of the service is the confirmation that the fuel was dispensed into a tank of the vehicle.
 7. The method according to claim 5 wherein validating the end of the authorized transaction further comprises verifying an hours of service for the known service provider and confirming that the authorized transaction occurs within a time period of the hours of service.
 8. The method according to claim 5 wherein proximity to the known service provider is validated utilizing a GPS component of the vehicle or validated utilizing miles traveled by the vehicle from a previous known location.
 9. The method according to claim 5 wherein the service is for repair of the vehicle and the confirmation of the end of the service is the confirmation that the vehicle is operating properly.
 10. The method according to claim 1 further comprising guiding the vehicle to the known service provider utilizing macro-navigation to travel from an origination site to a macro/micro route interface.
 11. The method according to claim 10 further comprising initiating a micro-navigation guidance protocol upon approach to the macro/micro route interface and guiding the vehicle using the micro-navigation guidance protocol from the macro/micro route interface to a terminal location within a destination site.
 12. The method according to claim 1 wherein the secure connection is made to a server for the known service provider.
 13. A system for a temporary secure connection between a device for a vehicle and a wireless authorized network, the system comprising: a vehicle comprising a vehicle device; and a known service provider comprising a physical location, a server and a wireless authorized network; wherein the vehicle device is configured to identify a wireless authorized network for a known service provider; wherein the vehicle device is configured to create a secure connection over the wireless authorized network between the vehicle device and the known service provider; and wherein the vehicle device is configured to initiate an authorized transaction for a service over the wireless authorized network with the known service provider, wherein the authorized transaction is authorized by an assigning authority associated with the vehicle.
 14. The system according to claim 13 wherein the vehicle device is configured to transmit sale and purchase information for the authorized transaction.
 15. The system according to claim 13 wherein the vehicle device is configured to validate the wireless authorized network based on proximity to the known service provider and the initiation of the service.
 16. The system according to claim 15 wherein the vehicle device is configured to confirm the end of the service.
 17. The system according to claim 15 wherein the vehicle device is configured to validate the end of the authorized transaction based on the end of the service and proximity to the known service provider.
 18. The system according to claim 17 wherein the service is for fuel for the vehicle and the confirmation of the end of the service is the confirmation that the fuel was dispensed into a tank of the vehicle.
 19. The system according to claim 17 wherein the vehicle device is configured to verify an hours of service for the known service provider and confirm that the authorized transaction occurs within a time period of the hours of service.
 20. The method according to claim 17 wherein proximity to the known service provider is validated utilizing a GPS component of the vehicle or is validated utilizing miles traveled by the vehicle from a previous known location. 